Automated access point mapping systems and methods

ABSTRACT

Wireless access point locations can be determined by processing a combination of wired and wireless telemetry. Wireless telemetry can be combined with backend network management information to isolate a set of access points within a radio frequency neighborhood cluster. Wired telemetry, including time domain reflectometer operations performed by a local switch, can be used to refine location estimates of the isolated set of access points. Trilateration can be used to pinpoint the access point locations and the pinpointed locations can be overlaid on a floor plan map.

TECHNICAL FIELD

The subject matter of this disclosure relates in general to the field of computer networking, and more particularly, to systems and methods for mapping wireless access points to a floor plan.

BACKGROUND

Wireless access points (APs) continue to become increasingly ubiquitous as WiFi networking continues to grow. It is often the case that a blanket of APs cover very large areas such as auditoriums, stadiums, large malls, entire communities, etc. As 802.11ac high throughput wireless networking protocols have become more prevalent, high density wireless deployments have likewise become an increasingly common practice.

However, installing new APs, for example to support high density wireless deployments, is typically a tedious and manual process. Floor maps, coordinates, network platform management labeling schemes, and the like must be taken into consideration by a technician when assessing network installation sites and installing new APs and other hardware. For example, an enterprise building may include between 25 and 30 APs on a given floor in order to cater to the needs of high capacity clients. As a result, manual installation and validation of APs can require a substantial amount of time and labor to perform and poor AP installations and/or locations can result in incorrect client location calculations as well as wasted debug cycles addressing wireless issues of a course of weeks, months, or even years.

BRIEF DESCRIPTION OF THE FIGURES

To provide a more complete understanding of the present disclosure and features and advantages thereof, reference is made to the following description, taken in conjunction with the accompanying drawings, in which:

FIG. 1 illustrates an example of a physical topology of an enterprise network in accordance with some examples;

FIG. 2 illustrates an example of a logical architecture for an enterprise network in accordance with some examples;

FIGS. 3A-3I illustrate examples of graphical user interfaces for a network management system in accordance with some examples;

FIG. 4 illustrates an example of a physical topology for a multi-site enterprise network in accordance with some examples;

FIG. 5A is a flowchart of an example of a method for determining network access point locations at a site in accordance with some examples;

FIGS. 5B(i)-(ii) illustrates user interface components for determining network access point locations in accordance with some examples;

FIG. 5C illustrates a radio frequency cluster neighborhood in accordance with some examples;

FIG. 5D illustrates an overlay of access point location estimates on a floor plan in accordance with some examples;

FIG. 5E illustrates an overlay of access point location estimates and sensors on a floor plan in accordance with some examples;

FIG. 5F illustrates an overlay of pinpointed access point location estimates on a floor plan in accordance with some examples; and

FIGS. 6A and 6B illustrate examples of systems in accordance with some examples.

DESCRIPTION OF EXAMPLE EMBODIMENTS

The detailed description set forth below is intended as a description of various configurations of embodiments and is not intended to represent the only configurations in which the subject matter of this disclosure can be practiced. The appended drawings are incorporated herein and constitute a part of the detailed description. The detailed description includes specific details for the purpose of providing a more thorough understanding of the subject matter of this disclosure. However, it will be clear and apparent that the subject matter of this disclosure is not limited to the specific details set forth herein and may be practiced without these details. In some instances, structures and components are shown in block diagram form in order to avoid obscuring the concepts of the subject matter of this disclosure.

Overview

Systems and methods are provided for locating access points (APs) in the context of a floor map. In particular, a combination of wired and wireless telemetry may be leveraged to determine current AP locations as well as determine installation sites and calibrations for new APs. AP locations can be estimated on a given floor based on macro levels network system information, such as, for example and without imputing limitation, a provided topology map, a discovery protocol, and/or a link layer discovery protocol (LLDP) neighbors identified by a backend infrastructure (e.g., DNA-C). Radio frequency (RF) neighbor relations information may be super imposed upon the estimated locations information to refine location estimates within a site. Additionally, switch time domain reflectometer (TDR) operations may be used to provide increased granularity in AP location information by using cable length estimates and relative positions of the APs on a shared floor. Further, trilateration based on AP data link (DL) signals can be done with floor view information of, for example, Active Sensor to further refine the locations of APs on a floor.

Example Embodiments

In some examples, telemetry from an infrastructure management backend and/or internal AP processes can be used in combination with time domain reflector (TDR) and/or active sensor telemetry to automatically identify and map APs to physical locations on a site. For example, a series of operations may be performed over multiple phases to process telemetry data in order to pinpoint AP locations on an office building floor to approximately an accuracy of one to two feet. As a result, manual logging, install site selection, and various updating processes may be accomplished automatically and with minimal technician manual labor.

In a first phase, a geographical site can be identified for mapping APs. For example, many wireless networks are deployed across multiple floors and buildings. In some examples, APs deployed, for example, within a ceiling of a floor possess respective L2 connections to one or more local access switches in order to provide network service via a connected core switch and/or router central hub. In particular, coarse AP location information can be provided by a network management backend or a respective network controller.

APs can be grouped based on respective connections to a central hub (e.g., core switch or router) and then further selected based on associations with particular access (e.g., local) switches. As a result, an AP neighborhood can be generated. In some examples, a geographical site may have one access switch per building or one per floor (e.g., based on AP desired AP density per floor, etc.). Discovery protocols (e.g., link layer discovery protocol (LLDP), Cisco® Discovery Protocol (CDP), etc.) can be used to identify APs for each switch. Further, customer-specific schema, such as naming conventions utilizing floor identifications, store identifications, building identifications, etc., can be used to further increase accuracy of the generated AP neighborhood.

A second phase may refine the coarse AP location information from the first phase using radio frequency (RF) constellation information. In particular, where APs include management frames according to 802.11ac protocols, the management frames may be used to measure distances between APs measured in decibel-milliwatts (dBm). A reverse-path model can be applied to the distances measured in dBm to generate a physical distance (e.g., meters, feet, etc.). In some examples, the reverse-path model can be specific to the respective site and may be generated at an earlier time (e.g., during an initial site layout or install) and saved in a network management backend or the like.

Using the physical distance measurements between APs, a bi-directional neighbor graph representing identified APs and intervening distances between each AP pairing can be constructed. The bi-directional neighbor graph may then be overlaid on coarse AP location information to generate a three-dimensional constellation of APs spread throughout the respective site.

The three-dimensional constellation of APs may be further refined in a third phase where, for example, RF leakage between floors and the like may be accounted for and AP mappings may be corrected. For example, it is often the case that an AP may observe neighbors via 802.11ac protocols on different floors of a shared building. As a result, the three-dimensional constellations generated in the first and second phases may include APs on multiple floors.

Time domain reflectometer (TDR) processes may be used to isolate APs of the three-dimensional constellation to a single floor. Local switches located on the floor (e.g., identified by the network management backend) may include TDR processes which can be use determine a cable length from the switch to each AP connected to the switch by wire. As a result, only APs connected to the switch, and thus on the floor to be mapped, may be selected from the three-dimensional constellation.

Additionally, the switch TDR processes can provide further refinement of the AP locations by incorporating respective cable lengths between each AP and the switch. A given AP may be determined, based on the cable length provided by the switch TDR, to be within a certain radius of the switch. Overlaying the radius onto the mapped and filtered AP constellation may provide, in some examples and without imputing limitation, a further refinement of an estimation of a respective AP location to approximately one meter accuracy.

In some examples, a fourth phase may be used to further refine AP location estimations by using trilateration from deployed sensors such as, for example and without imputing limitation, Active Sensors or the like. In particular, additional RF telemetry from sensors deployed throughout the floor may be used to further pinpoint APs using trilateration techniques associated with the sensors.

In some examples, each sensor may produce a report on received signal strength indicators (RSSIs) which may be used, for example, to monitor wireless accessibility, network health, etc. Here, the RSSIs may be used to calculate a distance between respective sensors and APs. Using the calculated distance, and known locations of the sensors within the map, the location estimates for each AP may be further refined. In some examples, additional indoor or outdoor decay factors may be applied to the calculated distances to provide a more robust distance determination and thus a more accurate update to the estimated AP locations.

As a result of the four phases, APs can be mapped to a floor plan with a level of accuracy of one meter or better. In some examples, the map may be provided to downstream services for rendering a floor plan with overlaid AP locations (e.g., to provide a visual appraisal of wireless coverage to an administrator, etc.) or to processes and algorithms for recommending installation locations for additional APs.

Backend network management processes are referred to in the phases discussed above. The disclosure now turns to a discussion of some examples of these backend network management processes before returning to a discussion of the access point mapping systems and methods in FIGS. 5A-F.

Intent-based networking is an approach for overcoming the deficiencies, discussed above and elsewhere in the present disclosure, of conventional enterprise networks. The motivation of intent-based networking is to enable a user to describe in plain language what he or she wants to accomplish (e.g., the user's intent) and have the network translate the user's objective into configuration and policy changes that are automatically propagated across a complex and heterogeneous computing environment. Thus, an intent-based network can abstract network complexity, automate much of the work of provisioning and managing the network typically handled by a network administrator, and assure secure operation and optimal performance of the network. As an intent-based network becomes aware of the users, devices, and things making connections in the network, it can automatically apply security permissions and service levels in accordance with the privileges and quality of experience (QoE) assigned to the users, devices, and things. Table 1 sets forth examples of intents and workflows that can be automated by an intent-based network to achieve a desired outcome.

TABLE 1 Examples of Intents and Associated Workflows Intent Workflow I need to scale out my Extend network segments; update load balancer application database configuration; configure quality of service (QoS) I have scheduled a Create high-definition (HD) video connection; prioritize with telemedicine session at end-to-end QoS; validate performance; keep the 10am communication safe; tear down connection after call I am rolling out a new IoT Create a new segment for all factory devices to connect to app for factory equipment the IoT app; isolate from other traffic; apply service level monitoring agreement (SLA); validate SLA; optimize traffic flow I need to deploy a secure Provision multiple networks and subnets; configure access multi-tier application control lists (ACLs) and firewall rules; advertise routing information

Some additional examples of use cases of an intent-based network:

-   -   An intent-based network can learn the performance needs of         applications and services and adapt the network from end-to-end         to achieve specified service levels;     -   Instead of sending technicians to every office, floor, building,         or branch, an intent-based network can discover and identify         devices and things as they connect, assign security and         micro-segmentation profiles according to established policies,         and continuously monitor access point performance to         automatically adjust for QoE;     -   Users can move freely among network segments, mobile device in         hand, and automatically connect with the correct security and         access privileges;     -   Switches, routers, and other network devices can be powered up         by local non-technical office personnel, and the network devices         can be configured remotely (by a user or by the network) via a         cloud management console with the appropriate policies as         defined by the intents for the specific location (e.g.,         permanent employee access, visiting employee access, guest         access, etc.); and     -   Machine learning and artificial intelligence agents running in         the network can continuously monitor and analyze network traffic         and connections, compare activity against pre-defined intents         such as application performance or security policies, detect         malware intrusions in encrypted traffic and automatically         isolate infected devices, and provide a historical record of         network events for analysis and troubleshooting.

FIG. 1 illustrates an example of a physical topology of an enterprise network 100 for providing intent-based networking. It should be understood that, for the enterprise network 100 and any network discussed herein, there can be additional or fewer nodes, devices, links, networks, or components in similar or alternative configurations. Example embodiments with different numbers and/or types of endpoints, nodes, cloud components, servers, software components, devices, virtual or physical resources, configurations, topologies, services, appliances, or deployments are also contemplated herein. Further, the enterprise network 100 can include any number or type of resources, which can be accessed and utilized by endpoints or network devices. The illustrations and examples provided herein are for clarity and simplicity.

In this example, the enterprise network 100 includes a management cloud 102 and a network fabric 120. Although shown as an external network or cloud to the network fabric 120 in this example, the management cloud 102 may alternatively or additionally reside on the premises of an organization or in a colocation center (in addition to being hosted by a cloud provider or similar environment). The management cloud 102 can provide a central management plane for building and operating the network fabric 120. The management cloud 102 can be responsible for forwarding configuration and policy distribution, as well as device management and analytics. The management cloud 102 can include one or more network controller appliances 104, one or more authentication, authorization, and accounting (AAA) appliances 106, one or more wireless local area network controllers (WLCs) 108, and one or more fabric control plane nodes 110. In other embodiments, one or more elements of the management cloud 102 may be co-located with the network fabric 120.

The network controller appliance(s) 104 can function as the command and control system for one or more network fabrics, and can house automated workflows for deploying and managing the network fabric(s). The network controller appliance(s) 104 can include automation, design, policy, provisioning, and assurance capabilities, among others, as discussed further below with respect to FIG. 2. In some embodiments, one or more Cisco Digital Network Architecture (Cisco DNA™) appliances can operate as the network controller appliance(s) 104.

The AAA appliance(s) 106 can control access to computing resources, facilitate enforcement of network policies, audit usage, and provide information necessary to bill for services. The AAA appliance can interact with the network controller appliance(s) 104 and with databases and directories containing information for users, devices, things, policies, billing, and similar information to provide authentication, authorization, and accounting services. In some embodiments, the AAA appliance(s) 106 can utilize Remote Authentication Dial-In User Service (RADIUS) or Diameter to communicate with devices and applications. In some embodiments, one or more Cisco® Identity Services Engine (ISE) appliances can operate as the AAA appliance(s) 106.

The WLC(s) 108 can support fabric-enabled access points attached to the network fabric 120, handling traditional tasks associated with a WLC as well as interactions with the fabric control plane for wireless endpoint registration and roaming. In some embodiments, the network fabric 120 can implement a wireless deployment that moves data-plane termination (e.g., VXLAN) from a centralized location (e.g., with previous overlay Control and Provisioning of Wireless Access Points (CAPWAP) deployments) to an access point/fabric edge node. This can enable distributed forwarding and distributed policy application for wireless traffic while retaining the benefits of centralized provisioning and administration. In some embodiments, one or more Cisco® Wireless Controllers, Cisco® Wireless LAN, and/or other Cisco DNA™-ready wireless controllers can operate as the WLC(s) 108.

The network fabric 120 can include fabric border nodes 122A and 122B (collectively, 122), fabric intermediate nodes 124A-D (collectively, 124), and fabric edge nodes 126A-F (collectively, 126). Although the fabric control plane node(s) 110 are shown to be external to the network fabric 120 in this example, in other embodiments, the fabric control plane node(s) 110 may be co-located with the network fabric 120. In embodiments where the fabric control plane node(s) 110 are co-located with the network fabric 120, the fabric control plane node(s) 110 may include a dedicated node or set of nodes or the functionality of the fabric control node(s) 110 may be implemented by the fabric border nodes 122.

The fabric control plane node(s) 110 can serve as a central database for tracking all users, devices, and things as they attach to the network fabric 120, and as they roam around. The fabric control plane node(s) 110 can allow network infrastructure (e.g., switches, routers, WLCs, etc.) to query the database to determine the locations of users, devices, and things attached to the fabric instead of using a flood and learn mechanism. In this manner, the fabric control plane node(s) 110 can operate as a single source of truth about where every endpoint attached to the network fabric 120 is located at any point in time. In addition to tracking specific endpoints (e.g., /32 address for IPv4, /128 address for IPv6, etc.), the fabric control plane node(s) 110 can also track larger summarized routers (e.g., IP/mask). This flexibility can help in summarization across fabric sites and improve overall scalability.

The fabric border nodes 122 can connect the network fabric 120 to traditional Layer 3 networks (e.g., non-fabric networks) or to different fabric sites. The fabric border nodes 122 can also translate context (e.g., user, device, or thing mapping and identity) from one fabric site to another fabric site or to a traditional network. When the encapsulation is the same across different fabric sites, the translation of fabric context is generally mapped 1:1. The fabric border nodes 122 can also exchange reachability and policy information with fabric control plane nodes of different fabric sites. The fabric border nodes 122 also provide border functions for internal networks and external networks. Internal borders can advertise a defined set of known subnets, such as those leading to a group of branch sites or to a data center. External borders, on the other hand, can advertise unknown destinations (e.g., to the Internet similar in operation to the function of a default route).

The fabric intermediate nodes 124 can operate as pure Layer 3 forwarders that connect the fabric border nodes 122 to the fabric edge nodes 126 and provide the Layer 3 underlay for fabric overlay traffic.

The fabric edge nodes 126 can connect endpoints to the network fabric 120 and can encapsulate/decapsulate and forward traffic from these endpoints to and from the network fabric. The fabric edge nodes 126 may operate at the perimeter of the network fabric 120 and can be the first points for attachment of users, devices, and things and the implementation of policy. In some embodiments, the network fabric 120 can also include fabric extended nodes (not shown) for attaching downstream non-fabric Layer 2 network devices to the network fabric 120 and thereby extend the network fabric. For example, extended nodes can be small switches (e.g., compact switch, industrial Ethernet switch, building automation switch, etc.) which connect to the fabric edge nodes via Layer 2. Devices or things connected to the fabric extended nodes can use the fabric edge nodes 126 for communication to outside subnets.

In this example, the network fabric can represent a single fabric site deployment which can be differentiated from a multi-site fabric deployment as discussed further below with respect to FIG. 4.

In some embodiments, all subnets hosted in a fabric site can be provisioned across every fabric edge node 126 in that fabric site. For example, if the subnet 10.10.10.0/24 is provisioned in a given fabric site, this subnet may be defined across all of the fabric edge nodes 126 in that fabric site, and endpoints located in that subnet can be placed on any fabric edge node 126 in that fabric. This can simplify IP address management and allow deployment of fewer but larger subnets. In some embodiments, one or more Cisco® Catalyst switches, Cisco Nexus® switches, Cisco Meraki® MS switches, Cisco® Integrated Services Routers (ISRs), Cisco® Aggregation Services Routers (ASRs), Cisco® Enterprise Network Compute Systems (ENCS), Cisco® Cloud Service Virtual Routers (CSRvs), Cisco Integrated Services Virtual Routers (ISRvs), Cisco Meraki® MX appliances, and/or other Cisco DNA-ready™ devices can operate as the fabric nodes 122, 124, and 126.

The enterprise network 100 can also include wired endpoints 130A, 130C, 130D, and 130F and wireless endpoints 130B and 130E (collectively, 130). The wired endpoints 130A, 130C, 130D, and 130F can connect by wire to fabric edge nodes 126A, 126C, 126D, and 126F, respectively, and the wireless endpoints 130B and 130E can connect wirelessly to wireless access points 128B and 128E (collectively, 128), respectively, which in turn can connect by wire to fabric edge nodes 126B and 126E, respectively. In some embodiments, Cisco Aironet® access points, Cisco Meraki® MR access points, and/or other Cisco DNA™-ready access points can operate as the wireless access points 128.

The endpoints 130 can include general purpose computing devices (e.g., servers, workstations, desktop computers, etc.), mobile computing devices (e.g., laptops, tablets, mobile phones, etc.), wearable devices (e.g., watches, glasses or other head-mounted displays (HMDs), ear devices, etc.), and so forth. The endpoints 130 can also include Internet of Things (IoT) devices or equipment, such as agricultural equipment (e.g., livestock tracking and management systems, watering devices, unmanned aerial vehicles (UAVs), etc.); connected cars and other vehicles; smart home sensors and devices (e.g., alarm systems, security cameras, lighting, appliances, media players, HVAC equipment, utility meters, windows, automatic doors, door bells, locks, etc.); office equipment (e.g., desktop phones, copiers, fax machines, etc.); healthcare devices (e.g., pacemakers, biometric sensors, medical equipment, etc.); industrial equipment (e.g., robots, factory machinery, construction equipment, industrial sensors, etc.); retail equipment (e.g., vending machines, point of sale (POS) devices, Radio Frequency Identification (RFID) tags, etc.); smart city devices (e.g., street lamps, parking meters, waste management sensors, etc.); transportation and logistical equipment (e.g., turnstiles, rental car trackers, navigational devices, inventory monitors, etc.); and so forth.

In some embodiments, the network fabric 120 can support wired and wireless access as part of a single integrated infrastructure such that connectivity, mobility, and policy enforcement behavior are similar or the same for both wired and wireless endpoints. This can bring a unified experience for users, devices, and things that is independent of the access media.

In integrated wired and wireless deployments, control plane integration can be achieved with the WLC(s) 108 notifying the fabric control plane node(s) 110 of joins, roams, and disconnects by the wireless endpoints 130 such that the fabric control plane node(s) can have connectivity information about both wired and wireless endpoints in the network fabric 120, and can serve as the single source of truth for endpoints connected to the network fabric. For data plane integration, the WLC(s) 108 can instruct the fabric wireless access points 128 to form a VXLAN overlay tunnel to their adjacent fabric edge nodes 126. The AP VXLAN tunnel can carry segmentation and policy information to and from the fabric edge nodes 126, allowing connectivity and functionality identical or similar to that of a wired endpoint. When the wireless endpoints 130 join the network fabric 120 via the fabric wireless access points 128, the WLC(s) 108 can onboard the endpoints into the network fabric 120 and inform the fabric control plane node(s) 110 of the endpoints' Media Access Control (MAC) addresses. The WLC(s) 108 can then instruct the fabric wireless access points 128 to form VXLAN overlay tunnels to the adjacent fabric edge nodes 126. Next, the wireless endpoints 130 can obtain IP addresses for themselves via Dynamic Host Configuration Protocol (DHCP). Once that completes, the fabric edge nodes 126 can register the IP addresses of the wireless endpoint 130 to the fabric control plane node(s) 110 to form a mapping between the endpoints' MAC and IP addresses, and traffic to and from the wireless endpoints 130 can begin to flow.

FIG. 2 illustrates an example of a logical architecture 200 for an enterprise network (e.g., the enterprise network 100). One of ordinary skill in the art will understand that, for the logical architecture 200 and any system discussed in the present disclosure, there can be additional or fewer component in similar or alternative configurations. The illustrations and examples provided in the present disclosure are for conciseness and clarity. Other embodiments may include different numbers and/or types of elements but one of ordinary skill the art will appreciate that such variations do not depart from the scope of the present disclosure. In this example, the logical architecture 200 includes a management layer 202, a controller layer 220, a network layer 230 (such as embodied by the network fabric 120), a physical layer 240 (such as embodied by the various elements of FIG. 1), and a shared services layer 250.

The management layer 202 can abstract the complexities and dependencies of other layers and provide a user with tools and workflows to manage an enterprise network (e.g., the enterprise network 100). The management layer 202 can include a user interface 204, design functions 206, policy functions 208, provisioning functions 210, assurance functions 212, platform functions 214, and base automation functions 216. The user interface 204 can provide a user a single point to manage and automate the network. The user interface 204 can be implemented within a web application/web server accessible by a web browser and/or an application/application server accessible by a desktop application, a mobile app, a shell program or other command line interface (CLI), an Application Programming Interface (e.g., restful state transfer (REST), Simple Object Access Protocol (SOAP), Service Oriented Architecture (SOA), etc.), and/or other suitable interface in which the user can configure network infrastructure, devices, and things that are cloud-managed; provide user preferences; specify policies, enter data; review statistics; configure interactions or operations; and so forth. The user interface 204 may also provide visibility information, such as views of a network, network infrastructure, computing devices, and things. For example, the user interface 204 can provide a view of the status or conditions of the network, the operations taking place, services, performance, a topology or layout, protocols implemented, running processes, errors, notifications, alerts, network structure, ongoing communications, data analysis, and so forth.

The design functions 206 can include tools and workflows for managing site profiles, maps and floor plans, network settings, and IP address management, among others. The policy functions 208 can include tools and workflows for defining and managing network policies. The provisioning functions 210 can include tools and workflows for deploying the network. The assurance functions 212 can use machine learning and analytics to provide end-to-end visibility of the network by learning from the network infrastructure, endpoints, and other contextual sources of information. The platform functions 214 can include tools and workflows for integrating the network management system with other technologies. The base automation functions 216 can include tools and workflows to support the policy functions 208, the provisioning functions 210, the assurance functions 212, and the platform functions 214.

In some embodiments, the design functions 206, the policy functions 208, the provisioning functions 210, the assurance functions 212, the platform functions 214, and the base automation functions 216 can be implemented as microservices in which respective software functions are implemented in multiple containers communicating with each rather than amalgamating all tools and workflows into a single software binary. Each of the design functions 206, policy functions 208, provisioning functions 210, assurance functions 212, and platform functions 214 can be viewed as a set of related automation microservices to cover the design, policy authoring, provisioning, assurance, and cross-platform integration phases of the network lifecycle. The base automation functions 214 can support the top-level functions by allowing users to perform certain network-wide tasks.

FIGS. 3A-3I illustrate examples of graphical user interfaces for implementing the user interface 204. Although FIGS. 3A-3I show the graphical user interfaces as comprising webpages displayed in a browser executing on a large form-factor general purpose computing device (e.g., server, workstation, desktop, laptop, etc.), the principles disclosed in the present disclosure are widely applicable to client devices of other form factors, including tablet computers, smart phones, wearable devices, or other small form-factor general purpose computing devices; televisions; set top boxes; IoT devices; and other electronic devices capable of connecting to a network and including input/output components to enable a user to interact with a network management system. One of ordinary skill will also understand that the graphical user interfaces of FIGS. 3A-3I are but one example of a user interface for managing a network. Other embodiments may include a fewer number or a greater number of elements.

FIG. 3A illustrates a graphical user interface 300A, which is an example of a landing screen or a home screen of the user interface 204. The graphical user interface 300A can include user interface elements for selecting the design functions 206, the policy functions 208, the provisioning functions 210, the assurance functions 212, and the platform functions 214. The graphical user interface 300A also includes user interface elements for selecting the base automation functions 216. In this example, the base automation functions 216 include:

-   -   A network discovery tool 302 for automating the discovery of         existing network elements to populate into inventory;     -   An inventory management tool 304 for managing the set of         physical and virtual network elements;     -   A topology tool 306 for visualizing the physical topology of         network elements;     -   An image repository tool 308 for managing software images for         network elements;     -   A command runner tool 310 for diagnosing one or more network         elements based on a CLI;     -   A license manager tool 312 for administering visualizing         software license usage in the network;     -   A template editor tool 314 for creating and authoring CLI         templates associated with network elements in a design profile;     -   A network PnP tool 316 for supporting the automated         configuration of network elements;     -   A telemetry tool 318 for designing a telemetry profile and         applying the telemetry profile to network elements; and     -   A data set and reports tool 320 for accessing various data sets,         scheduling data extracts, and generating reports in multiple         formats (e.g., Post Document Format (PDF), comma-separate values         (CSV), Tableau, etc.), such as an inventory data report, a         software image management (SWIM) server report, and a client         data report, among others.

FIG. 3B illustrates a graphical user interface 300B, an example of a landing screen for the design functions 206. The graphical user interface 300B can include user interface elements for various tools and workflows for logically defining an enterprise network. In this example, the design tools and workflows include:

-   -   A network hierarchy tool 322 for setting up the geographic         location, building, and floor plane details, and associating         these with a unique site id;     -   A network settings tool 324 for setting up network servers         (e.g., Domain Name System (DNS), DHCP, AAA, etc.), device         credentials, IP address pools, service provider profiles (e.g.,         QoS classes for a WAN provider), and wireless settings;     -   An image management tool 326 for managing software images and/or         maintenance updates, setting version compliance, and downloading         and deploying images;     -   A network profiles tool 328 for defining LAN, WAN, and WLAN         connection profiles (including Service Set Identifiers (SSIDs));         and     -   An authentication template tool 330 for defining modes of         authentication (e.g., closed authentication, Easy Connect, open         authentication, etc.).

The output of the design workflow 206 can include a hierarchical set of unique site identifiers that define the global and forwarding configuration parameters of the various sites of the network. The provisioning functions 210 may use the site identifiers to deploy the network.

FIG. 3C illustrates a graphical user interface 300C, an example of a landing screen for the policy functions 208. The graphical user interface 300C can include various tools and workflows for defining network policies. In this example, the policy design tools and workflows include:

-   -   A policy dashboard 332 for viewing virtual networks, group-based         access control policies, IP-based access control policies,         traffic copy policies, scalable groups, and IP network groups.         The policy dashboard 332 can also show the number of policies         that have failed to deploy. The policy dashboard 332 can provide         a list of policies and the following information about each         policy: policy name, policy type, policy version (e.g.,         iteration of policy which can be incremented each time the         policy changes, user who has modified the policy, description,         policy scope (e.g., user and device groups or applications that         the policy affects), and timestamp;     -   A group-based access control policies tool 334 for managing         group-based access controls or SGACLs. A group-based access         control policy can define scalable groups and an access contract         (e.g., rules that make up the access control policies, such as         permit or deny when traffic matches on the policy);     -   An IP-based access control policies tool 336 for managing         IP-based access control policies. An IP-based access control can         define an IP network group (e.g., IP subnets that share same         access control requirements) and an access contract;     -   An application policies tool 338 for configuring QoS for         application traffic. An application policy can define         application sets (e.g., sets of applications that with similar         network traffic needs) and a site scope (e.g., the site to which         an application policy is defined);     -   A traffic copy policies tool 340 for setting up an Encapsulated         Remote Switched Port Analyzer (ERSPAN) configuration such that         network traffic flow between two entities is copied to a         specified destination for monitoring or troubleshooting. A         traffic copy policy can define the source and destination of the         traffic flow to copy and a traffic copy contract that specifies         the device and interface where the copy of traffic is sent; and     -   A virtual network policies tool 343 for segmenting the physical         network into multiple logical networks.

The output of the policy workflow 208 can include a set of virtual networks, security groups, and access and traffic policies that define the policy configuration parameters of the various sites of the network. The provisioning functions 210 may use the virtual networks, groups, and policies for deployment in the network.

FIG. 3D illustrates a graphical user interface 300D, an example of a landing screen for the provisioning functions 210. The graphical user interface 300D can include various tools and workflows for deploying the network. In this example, the provisioning tools and workflows include:

-   -   A device provisioning tool 344 for assigning devices to the         inventory and deploying the required settings and policies, and         adding devices to sites; and     -   A fabric provisioning tool 346 for creating fabric domains and         adding devices to the fabric.

The output of the provisioning workflow 210 can include the deployment of the network underlay and fabric overlay, as well as policies (defined in the policy workflow 208).

FIG. 3E illustrates a graphical user interface 300E, an example of a landing screen for the assurance functions 212. The graphical user interface 300E can include various tools and workflows for managing the network. In this example, the assurance tools and workflows include:

-   -   A health overview tool 344 for providing a global view of the         enterprise network, including network infrastructure devices and         endpoints. The user interface element (e.g., drop-down menu, a         dialog box, etc.) associated with the health overview tool 344         can also be toggled to switch to additional or alternative         views, such as a view of the health of network infrastructure         devices alone, a view of the health of all wired and wireless         clients, and a view of the health of applications running in the         network as discussed further below with respect to FIGS. 3F-3H;     -   An assurance dashboard tool 346 for managing and creating custom         dashboards;     -   An issues tool 348 for displaying and troubleshooting network         issues; and     -   A sensor management tool 350 for managing sensor-driven tests.

The graphical user interface 300E can also include a location selection user interface element 352, a time period selection user interface element 354, and a view type user interface element 356. The location selection user interface element 354 can enable a user to view the overall health of specific sites (e.g., as defined via the network hierarchy tool 322) and/or network domains (e.g., LAN, WLAN, WAN, data center, etc.). The time period selection user interface element 356 can enable display of the overall health of the network over specific time periods (e.g., last 3 hours, last 24 hours, last 7 days, custom, etc.). The view type user interface element 355 can enable a user to toggle between a geographical map view of the sites of the network (not shown) or a hierarchical site/building view (as shown).

Within the hierarchical site/building view, rows can represent the network hierarchy (e.g. sites and buildings as defined by the network hierarchy tool 322); column 358 can indicate the number of healthy clients as a percentage; column 360 can indicate the health of wireless clients by a score (e.g., 1-10), color and/or descriptor (e.g., red or critical associated with a health score 1 to 3 indicating the clients have critical issues, orange or warning associated with a health score of 4 to 7 indicating warnings for the clients, green or no errors or warnings associated with a health score of 8 to 10, grey or no data available associated with a health score of null or 0), or other indicator; column 362 can indicate the health of wired clients by score, color, descriptor, and so forth; column 364 can include user interface elements for drilling down to the health of the clients associated with a hierarchical site/building; column 366 can indicate the number of healthy network infrastructure devices as a percentage; column 368 can indicate the health of access switches by score, color, descriptor, and so forth; column 370 can indicate the health of core switches by score, color, descriptor, and so forth; column 372 can indicate the health of distribution switches by score, color, descriptor, and so forth; column 374 can indicate the health of routers by score, color, descriptor, and so forth; column 376 can indicate the health of WLCs by score, color, descriptor, and so forth; column 378 can indicate the health of other network infrastructure devices by score, color, descriptor, and so forth; and column 380 can include user interface elements for drilling down to the health of the network infrastructure devices associated with a hierarchical site/building. In other embodiments, client devices may be grouped in other ways besides wired or wireless, such as by device type (e.g., desktop, laptop, mobile phone, IoT device or more specific type of IoT device, etc.), manufacturer, model, operating system, and so forth. Likewise, network infrastructure devices can also be grouped along these and other ways in additional embodiments.

The graphical user interface 300E can also include an overall health summary user interface element (e.g., a view, pane, tile, card, container, widget, dashlet, etc.) that includes a client health summary user interface element 384 indicating the number of healthy clients as a percentage, a color coded trend chart 386 indicating that percentage over a specific time period (e.g., as selected by the time period selection user interface element 354), a user interface element 388 breaking down the number of healthy clients as a percentage by client type (e.g., wireless, wired), a network infrastructure health summary user interface element 390 indicating the number of health network infrastructure devices as a percentage, a color coded trend chart 392 indicating that percentage over a specific time period, and a user interface element 394 breaking down the number of network infrastructure devices as a percentage by network infrastructure device type (e.g., core switch, access switch, distribution switch, etc.).

The graphical user interface 300E can also include an issues user interface element 396 listing issues, if any, that must be addressed. Issues can be sorted based on timestamp, severity, location, device type, and so forth. Each issue may be selected to drill down to view a more detailed view of the selected issue.

FIG. 3F illustrates a graphical user interface 300F, an example of a screen for an overview of the health of network infrastructure devices alone, which may be navigated to, for instance, by toggling the health overview tool 344. The graphical user interface 300F can include a timeline slider 398 for selecting a more granular time range than a time period selection user interface element (e.g., the time period selection user interface element 354). The graphical user interface 300F can also include similar information to that shown in the graphical user interface 300E, such as a user interface element comprising a hierarchical site/building view and/or geographical map view similar to that of the graphical user interface 300E (except providing information only for network infrastructure devices) (not shown here), the number of healthy network infrastructure devices as a percentage 390, the color coded trend charts 392 indicating that percentage by device type, the breakdown of the number of healthy network infrastructure devices by device type 394, and so forth. In addition, the graphical user interface 300F can display a view of the health of network infrastructure devices by network topology (not shown). This view can be interactive, such as by enabling a user to zoom in or out, pan left or right, or rotate the topology (e.g., by 90 degrees).

In this example, the graphical user interface 300F also includes a color coded trend chart 3002 showing the performance of the network infrastructure devices over a specific time period; network health by device type tabs including a system health chart 3004 providing system monitoring metrics (e.g., CPU utilization, memory utilization, temperature, etc.), a data plane connectivity chart 3006 providing data plane metrics, such as uplink availability and link errors, and a control plane connectivity chart 3008 providing control plane metrics for each device type; an AP analytics user interface element including an up and down color coded chart 3010 that provides AP status information (e.g., the number of APs connected to the network, and the number of APs not connected to the network, etc.) and a top number N of APs by client count chart 3012 that provides information about the APs that have the highest number of clients; a network devices table 3014 enabling a user to filter (e.g., by device type, health, or custom filters), view, and export network device information. A detailed view of the health of each network infrastructure device can also be provided by selecting that network infrastructure device in the network devices table 3014.

FIG. 3G illustrates a graphical user interface 300G, an example of a screen for an overview of the health of client devices, which may be navigated to, for instance, by toggling the health overview tool 344. The graphical user interface 300G can include an SSID user interface selection element 3016 for viewing the health of wireless clients by all SSIDs or a specific SSID, a band frequency user interface selection element 3018 for viewing the health of wireless clients by all band frequencies or a specific band frequency (e.g., 2.4 GHz, 5 GHz, etc.), and a time slider 3020 that may operate similarly to the time slider 398.

The graphical user interface 300G can also include a client health summary user interface element that provides similar information to that shown in the graphical user interface 300E, such as the number of healthy clients as a percentage 384 and a color coded trend chart 386 indicating that percentage over a specific time period for each grouping of client devices (e.g., wired/wireless, device type, manufacturer, model, operating system, etc.). In addition, the client health summary user interface element can include a color-coded donut chart that provides a count of poor (e.g., red and indicating a client health score of 1 to 3), fair (e.g., orange and indicating a client health score of 4 to 7), good (e.g., green and indicating a health score of 8 to 10), and inactive (e.g., grey and indicating a health score that is null or 0) client devices. The count of client devices associated with each color, health score, health descriptor, and so forth may be displayed by a selection gesture directed toward that color (e.g., tap, double tap, long press, hover, click, right-click, etc.).

The graphical user interface 300G can also include a number of other client health metric charts in all sites or a selected site over a specific time period, such as:

-   -   Client onboarding times 3024;     -   Received Signal Strength Indications (RSSIs) 3026;     -   Connectivity signal-to-noise ratios (SNRs) 3028;     -   Client counts per SSID 3030;     -   Client counts per band frequency 3032;     -   DNS requests and response counters (not shown); and     -   Connectivity physical link state information 3034 indicating the         distribution of wired client devices that had their physical         links up, down, and had errors.

In addition, the graphical user interface 300G can include a client devices table 3036 enabling a user to filter (e.g., by device type, health, data (e.g., onboarding time>threshold, association time>threshold, DHCP>threshold, AAA>threshold, RSSI>threshold, etc.), or custom filters), view, and export client device information (e.g., user identifier, hostname, MAC address, IP address, device type, last heard, location, VLAN identifier, SSID, overall health score, onboarding score, connection score, network infrastructure device to which the client device is connected, etc.). A detailed view of the health of each client device can also be provided by selecting that client device in the client devices table 3036.

FIG. 3H illustrates a graphical user interface 300H, an example of a screen for an overview of the health of applications, which may be navigated to, for instance, by the toggling the health overview tool 344. The graphical user interface 300H can include application health summary user interface element including a percentage 3038 of the number of healthy applications as a percentage, a health score 3040 for each application or type of application (e.g., business relevant, business irrelevant, default; HTTP, VoIP, chat, email, bulk transfer, multimedia/streaming, etc.) running in the network, a top number N of applications by usage chart 3042. The health score 3040 can be calculated based on an application's qualitative metrics, such as packet loss, network latency, and so forth.

In addition, the graphical user interface 300H can also include an applications table 3044 enabling a user to filter (e.g., by application name, domain name, health, usage, average throughput, traffic class, packet loss, network latency, application latency, custom filters, etc.), view, and export application information. A detailed view of the health of each application can also be provided by selecting that application in the applications table 3044.

FIG. 3I illustrates an example of a graphical user interface 300I, an example of a landing screen for the platform functions 210. The graphical user interface 300C can include various tools and workflows for integrating with other technology systems. In this example, the platform integration tools and workflows include:

-   -   A bundles tool 3046 for managing packages of domain-specific         APIs, workflows, and other features for network programming and         platform integration;     -   A developer toolkit 3048 for accessing an API catalog listing         the available APIs and methods (e.g., GET, PUT, POST, DELETE,         etc.), descriptions, runtime parameters, return codes, model         schemas, and so forth. In some embodiments, the developer         toolkit 3048 can also include a “Try It” button to permit a         developer to experiment with a particular API to better         understand its behavior;     -   A runtime dashboard 3050 for viewing and analyzing basic metrics         or API and integration flow usage;     -   A platform settings tool 3052 to view and set global or         bundle-specific settings that define integration destinations         and event consumption preferences; and     -   A notifications user interface element 3054 for presenting         notifications regarding the availability of software updates,         security threats, and so forth.

Returning to FIG. 2, the controller layer 220 can include subsystems for the management layer 220 and may include a network control platform 222, a network data platform 224, and AAA services 226. These controller subsystems can form an abstraction layer to hide the complexities and dependencies of managing many network elements and protocols.

The network control platform 222 can provide automation and orchestration services for the network layer 230 and the physical layer 240, and can include the settings, protocols, and tables to automate management of the network and physical layers. For example, the network control platform 230 can provide the design functions 206, the provisioning functions 208 212. In addition, the network control platform 230 can include tools and workflows for discovering switches, routers, wireless controllers, and other network infrastructure devices (e.g., the network discovery tool 302); maintaining network and endpoint details, configurations, and software versions (e.g., the inventory management tool 304); Plug-and-Play (PnP) for automating deployment of network infrastructure (e.g., the network PnP tool 316), Path Trace for creating visual data paths to accelerate the troubleshooting of connectivity problems, Easy QoS for automating quality of service to prioritize applications across the network, and Enterprise Service Automation (ESA) for automating deployment of physical and virtual network services, among others. The network control platform 222 can communicate with network elements using Network Configuration (NETCONF)/Yet Another Next Generation (YANG), Simple Network Management Protocol (SNMP), Secure Shell (SSH)/Telnet, and so forth. In some embodiments, the Cisco® Network Control Platform (NCP) can operate as the network control platform 222

The network data platform 224 can provide for network data collection, analytics, and assurance, and may include the settings, protocols, and tables to monitor and analyze network infrastructure and endpoints connected to the network. The network data platform 224 can collect multiple types of information from network infrastructure devices, including syslog, SNMP, NetFlow, Switched Port Analyzer (SPAN), and streaming telemetry, among others. The network data platform 224 can also collect use contextual information shared from

In some embodiments, one or more Cisco DNA™ Center appliances can provide the functionalities of the management layer 210, the network control platform 222, and the network data platform 224. The Cisco DNA™ Center appliances can support horizontal scalability by adding additional Cisco DNA™ Center nodes to an existing cluster; high availability for both hardware components and software packages; backup and store mechanisms to support disaster discovery scenarios; role-based access control mechanisms for differentiated access to users, devices, and things based on roles and scope; and programmable interfaces to enable integration with third party vendors. The Cisco DNA™ Center appliances can also be cloud-tethered to provide for the upgrade of existing functions and additions of new packages and applications without having to manually download and install them.

The AAA services 226 can provide identity and policy services for the network layer 230 and physical layer 240, and may include the settings, protocols, and tables to support endpoint identification and policy enforcement services. The AAA services 226 can provide tools and workflows to manage virtual networks and security groups, and to create group-based policies and contracts. The AAA services 226 can identify and profile network infrastructure devices and endpoints using AAA/RADIUS, 802.1X, MAC Authentication Bypass (MAB), web authentication, and EasyConnect, among others. The AAA services 226 can also collect and use contextual information from the network control platform 222, the network data platform 224, and the shared services 250, among others. In some embodiments, Cisco® ISE can provide the AAA services 226.

The network layer 230 can be conceptualized as a composition of two layers, an underlay 234 comprising physical and virtual network infrastructure (e.g., routers, switches, WLCs, etc.) and a Layer 3 routing protocol for forwarding traffic, and an overlay 232 comprising a virtual topology for logically connecting wired and wireless users, devices, and things and applying services and policies to these entities. Network elements of the underlay 234 can establish connectivity between each other, such as via Internet Protocol (IP). The underlay may use any topology and routing protocol.

In some embodiments, the network controller 104 can provide a local area network (LAN) automation service, such as implemented by Cisco DNA™ Center LAN Automation, to automatically discover, provision, and deploy network devices. Once discovered, the automated underlay provisioning service can leverage Plug and Play (PnP) to apply the required protocol and network address configurations to the physical network infrastructure. In some embodiments, the LAN automation service may implement the Intermediate System to Intermediate System (IS-IS) protocol. Some of the advantages of IS-IS include neighbor establishment without IP protocol dependencies, peering capability using loopback addresses, and agnostic treatment of IPv4, IPv6, and non-IP traffic.

The overlay 232 can be a logical, virtualized topology built on top of the physical underlay 234, and can include a fabric data plane, a fabric control plane, and a fabric policy plane. In some embodiments, the fabric data plane can be created via packet encapsulation using Virtual Extensible LAN (VXLAN) with Group Policy Option (GPO). Some of the advantages of VXLAN-GPO include its support for both Layer 2 and Layer 3 virtual topologies (overlays), and its ability to operate over any IP network with built-in network segmentation.

In some embodiments, the fabric control plane can implement Locator/ID Separation Protocol (LISP) for logically mapping and resolving users, devices, and things. LISP can simplify routing by removing the need for each router to process every possible IP destination address and route. LISP can achieve this by moving remote destination to a centralized map database that allows each router to manage only its local routs and query the map system to locate destination endpoints.

The fabric policy plane is where intent can be translated into network policy. That is, the policy plane is where the network operator can instantiate logical network policy based on services offered by the network fabric 120, such as security segmentation services, quality of service (QoS), capture/copy services, application visibility services, and so forth.

Segmentation is a method or technology used to separate specific groups of users or devices from other groups for the purpose of reducing congestion, improving security, containing network problems, controlling access, and so forth. As discussed, the fabric data plane can implement VXLAN encapsulation to provide network segmentation by using the virtual network identifier (VNI) and Scalable Group Tag (SGT) fields in packet headers. The network fabric 120 can support both macro-segmentation and micro-segmentation. Macro-segmentation logically separates a network topology into smaller virtual networks by using a unique network identifier and separate forwarding tables. This can be instantiated as a virtual routing and forwarding (VRF) instance and referred to as a virtual network (VN). That is, a VN is a logical network instance within the network fabric 120 defined by a Layer 3 routing domain and can provide both Layer 2 and Layer 3 services (using the VXLAN VNI to provide both Layer 2 and Layer 3 segmentation). Micro-segmentation logically separates user or device groups within a VN, by enforcing source to destination access control permissions, such as by using access control lists (ACLs). A scalable group is a logical object identifier assigned to a group of users, devices, or things in the network fabric 120. It can be used as source and destination classifiers in Scalable Group ACLs (SGACLs). The SGT can be used to provide address-agnostic group-based policies.

In some embodiments, the fabric control plane node 110 may implement the Locator/Identifier Separation Protocol (LISP) to communicate with one another and with the management cloud 102. Thus, the control plane nodes may operate a host tracking database, a map server, and a map resolver. The host tracking database can track the endpoints 130 connected to the network fabric 120 and associate the endpoints to the fabric edge nodes 126, thereby decoupling an endpoint's identifier (e.g., IP or MAC address) from its location (e.g., closest router) in the network.

The physical layer 240 can include network infrastructure devices, such as switches and routers 110, 122, 124, and 126 and wireless elements 108 and 128 and network appliances, such as the network controller appliance(s) 104, and the AAA appliance(s) 106.

The shared services layer 250 can provide an interface to external network services, such as cloud services 252; Domain Name System (DNS), DHCP, IP Address Management (IPAM), and other network address management services 254; firewall services 256; Network as a Sensor (Naas)/Encrypted Threat Analytics (ETA) services; and Virtual Network Functions (VNFs) 260; among others. The management layer 202 and/or the controller layer 220 can share identity, policy, forwarding information, and so forth via the shared services layer 250 using APIs.

FIG. 4 illustrates an example of a physical topology for a multi-site enterprise network 400. In this example, the network fabric includes fabric sites 420A and 420B. The fabric site 420A can include a fabric control node 410A, fabric border nodes 422A and 422B, fabric intermediate nodes 424A and 424B (shown here in dashed line and not connected to the fabric border nodes or the fabric edge nodes for simplicity), and fabric edge nodes 426A-D. The fabric site 420B can include a fabric control node 4106, fabric border nodes 422C-E, fabric intermediate nodes 424C and 424D, and fabric edge nodes 426D-F. Multiple fabric sites corresponding to a single fabric, such as the network fabric of FIG. 4, can be interconnected by a transit network. A transit network can be a portion of a network fabric that has its own control plane nodes and border nodes but does not have edge nodes. In addition, a transit network shares at least one border node with each fabric site that it interconnects.

In general, a transit network connects a network fabric to the external world. There are several approaches to external connectivity, such as a traditional IP network 436, traditional WAN 438A, Software-Defined WAN (SD-WAN) (not shown), or Software-Defined Access (SD-Access) 438B. Traffic across fabric sites, and to other types of sites, can use the control plane and data plane of the transit network to provide connectivity between these sites. A local border node can operate as the handoff point from the fabric site, and the transit network can deliver traffic to other sites. The transit network may use additional features. For example, if the transit network is a WAN, then features like performance routing may also be used. To provide end-to-end policy and segmentation, the transit network should be capable of carrying endpoint context information (e.g., VRF, SGT) across the network. Otherwise, a re-classification of the traffic may be needed at the destination site border.

The local control plane in a fabric site may only hold state relevant to endpoints that are connected to edge nodes within the local fabric site. The local control plane can register local endpoints via local edge nodes, as with a single fabric site (e.g., the network fabric 120). An endpoint that isn't explicitly registered with the local control plane may be assumed to be reachable via border nodes connected to the transit network. In some embodiments, the local control plane may not hold state for endpoints attached to other fabric sites such that the border nodes do not register information from the transit network. In this manner, the local control plane can be independent of other fabric sites, thus enhancing overall scalability of the network.

The control plane in the transit network can hold summary state for all fabric sites that it interconnects. This information can be registered to the transit control plane by border from different fabric sites. The border nodes can register EID information from the local fabric site into the transit network control plane for summary EIDs only and thus further improve scalability.

The multi-site enterprise network 400 can also include a shared services cloud 432. The shared services cloud 432 can include one or more network controller appliances 404, one or more AAA appliances 406, and other shared servers (e.g., DNS; DHCP; IPAM; SNMP and other monitoring tools; NetFlow, syslog, and other data collectors, etc.) may reside. These shared services can generally reside outside of the network fabric and in a global routing table (GRT) of an existing network. In this case, some method of inter-VRF routing may be required. One option for inter-VRF routing is to use a fusion router, which can be an external router that performs inter-VRF leaking (e.g., import/export of VRF routes) to fuse the VRFs together. Multi-Protocol can be used for this route exchange since it can inherently prevent routing loops (e.g., using the AS_PATH attribute). Other routing protocols can also be used but may require complex distribute-lists and prefix-lists to prevent loops.

However, there can be several disadvantages in using a fusion router to achieve inter-VN communication, such as route duplication because routes leaked from one VRF to another are programmed in hardware tables and can result in more TCAM utilization, manual configuration at multiple touch points wherever route-leaking is implemented, loss of SGT context because SGTs may not be maintained across VRFs and must be re-classified once the traffic enters the other VRF, and traffic hairpinning because traffic may need to be routed to the fusion router, and then back to the fabric border node.

SD-Access Extranet can provide a flexible and scalable method for achieving inter-VN communications by avoiding route duplication because inter-VN lookup occurs in the fabric control plane (e.g., software) such that route entries do not need to be duplicated in hardware; providing a single touchpoint because the network management system (e.g., Cisco DNA™ Center) can automate the inter-VN lookup policy, making it a single point of management; maintaining SGT context because the inter-VN lookup occurs in the control plane node(s) (e.g., software), and avoids hair-pinning because inter-VN forwarding can occur at the fabric edge (e.g., the same intra-VN) so traffic does not need to hairpin at the border node. Another advantage is that a separate VN can be made for each of the common resources that are needed (e.g., a Shared Services VN, an Internet VN, a data center VN, etc.).

FIG. 5A depicts a method 500 for generating refined access point (AP) location estimates. In particular, the AP location estimates may be overlaid on a floor plan or the like to provide a visual indication of AP locations throughout a particular floor of a building or geographical site.

At step 502, a geographic site is identified by accessing ceiling-installed local access switches in an area to be mapped. In particular, a backend network management system, for example as discussed above in reference to FIGS. 1-4, may be used to access the ceiling-installed local access switches. FIGS. 5B(i)-5B(ii) depict example graphical user interfaces (GUIs) 520, 525 for accessing switches for identifying geographic sites.

In particular, GUI 520 includes a switch icon 524, which may be interacted with to retrieve additional information related to a particular switch. In some examples, interaction with switch icon 524 may bring up GUI 525 to provide detailed information. GUI 520 includes a linkage to AP icons 522, which correspond to unified APs connected to the particular switch by a wired connection. GUI 520 also includes a linkage to wired host icons 523, which correspond to hosts (e.g., desktop computers, servers, etc.) connected to the particular switch by a wired connection.

GUI 525 shows a detailed view of a local 530. In particular, local switch 530 includes switch address information 529. Switch address information 529 includes a switch name prefix 526, a site identifier 527, and a customer (e.g., client company, etc.) domain 528. In particular, site identifier 527 may be used to identify switches within a specific geographic location. For example, all switches associated with a particular site identifier 527 may be accessed to identify all APs across the corresponding site. APs connected to local switch 530 may be associated with an AP 532.

Returning to FIG. 5A, at step 504, radio frequency (RF) constellation information based on 802.11 management frames transmitted by APs associated with the geographic site are accessed. At step 506, a reverse-path loss model is applied to the accessed RF constellation information to determine physical distances between APs of the RF constellation.

In particular, FIG. 5C depicts a RF constellation 540 which can be constructed based on management frames, such as inter-AP neighbor discovery frames or the like, which may be transmitted between APs and respective information may be retrieved via the backend network management service. For example, APs 542 may each construct a list of receiving neighbors (e.g., neighboring APs that can receive transmissions from a respective AP) and a list of transmitting neighbors (e.g., neighboring APs that can receive transmissions from the respective AP) using received signal strength indicator (RSSI) information for transmitting and receiving neighbors. The RF constellation can then be generated using the RSSI information to generate inter-AP RF linkages 544.

Reverse-path loss models can then be used to determine physical distances between the APs based on the RF linkages 544 and signal strength information received as part of the RSSI information. In some examples, the backend network management may include various path loss models for indoor environments, outdoor environments, open office environments, and so on. Likewise, a site-specific path loss model may be generated at an earlier time and used for determining distances based on the RF linkages 544. Nevertheless, using an appropriate reverse-path loss model, physical distances (e.g., meters, feet, etc.) between APs can be determined based on the RF linkages 544.

FIG. 5D depicts an illustration of a floor plan 550 including AP location estimates 554, refined according to step 506, overlaid upon a map 552 of a respective floor. Here, location estimates 554 are rendered as circles encompassing a potential area in which an AP may be located.

Returning to FIG. 5A, at step 508 AP locations are estimated within the area to be mapped by determining cable lengths between respective APs and the local access switches using respective switch time domain reflectometer (TDR) operations (e.g., provided by respective switches) and based on the determined physical distances between access points from step 506.

At step 510, trilateration is applied to received RSSIs reported by a sensor beacon to further refine the AP location estimates. Sensors, such as Active Sensors, may be deployed throughout a floor and may be accessible to the backend network management service. The sensors may perform wireless network analytics and generate reports on, for example and without imputing limitation, signal strength, consistency, logs, wireless network traffic information, etc. Sensor signal strength reports can be processed through trilateration to further pinpoint AP locations relative to the deployed sensors and/or on the floor where sensor locations may be already mapped.

FIG. 5E depicts an illustration of updated floor plan 560 updated to include AP location estimates 554, refined according to step 510 applying trilateration to sensor RSSI reports, overlaid upon map 552. Sensors 562 are mapped, either manually or through an automated process, within map 552 and thus are able to provide trilateration for further refining location estimates 554.

FIG. 5F depicts an illustration of further updated floor plan 570, which includes further refined location estimates 572 based on refine location estimates 554 and data from sensors 562 (e.g., trilateration information, etc.). As a result, further updated floor plan 570 includes further refined location estimates 572 for APs that have a range of approximately one to two meters in coverage.

Returning to FIG. 5A, at step 512, the refined AP location estimates are provided to downstream processes such as a floor plan renderer or an AP installation site recommender. In some examples, further updated floor plan 570 is generated and displayed, for example, to an administrator for AP installation planning or the like.

FIG. 6A and FIG. 6B illustrate systems in accordance with various embodiments. The more appropriate system will be apparent to those of ordinary skill in the art when practicing the various embodiments. Persons of ordinary skill in the art will also readily appreciate that other systems are possible.

FIG. 6A illustrates an example of a bus computing system 600 wherein the components of the system are in electrical communication with each other using a bus 605. The computing system 600 can include a processing unit (CPU or processor) 610 and a system bus 605 that may couple various system components including the system memory 615, such as read only memory (ROM) 620 and random access memory (RAM) 625, to the processor 610. The computing system 600 can include a cache 612 of high-speed memory connected directly with, in close proximity to, or integrated as part of the processor 610. The computing system 600 can copy data from the memory 615, ROM 620, RAM 625, and/or storage device 630 to the cache 612 for quick access by the processor 610. In this way, the cache 612 can provide a performance boost that avoids processor delays while waiting for data. These and other modules can control the processor 610 to perform various actions. Other system memory 615 may be available for use as well. The memory 615 can include multiple different types of memory with different performance characteristics. The processor 610 can include any general purpose processor and a hardware module or software module, such as module 1 632, module 2 634, and module 3 636 stored in the storage device 630, configured to control the processor 610 as well as a special-purpose processor where software instructions are incorporated into the actual processor design. The processor 610 may essentially be a completely self-contained computing system, containing multiple cores or processors, a bus, memory controller, cache, etc. A multi-core processor may be symmetric or asymmetric.

To enable user interaction with the computing system 600, an input device 645 can represent any number of input mechanisms, such as a microphone for speech, a touch-protected screen for gesture or graphical input, keyboard, mouse, motion input, speech and so forth. An output device 635 can also be one or more of a number of output mechanisms known to those of skill in the art. In some instances, multimodal systems can enable a user to provide multiple types of input to communicate with the computing system 600. The communications interface 640 can govern and manage the user input and system output. There may be no restriction on operating on any particular hardware arrangement and therefore the basic features here may easily be substituted for improved hardware or firmware arrangements as they are developed.

The storage device 630 can be a non-volatile memory and can be a hard disk or other types of computer readable media which can store data that are accessible by a computer, such as magnetic cassettes, flash memory cards, solid state memory devices, digital versatile disks, cartridges, random access memory, read only memory, and hybrids thereof.

As discussed above, the storage device 630 can include the software modules 632, 634, 636 for controlling the processor 610. Other hardware or software modules are contemplated. The storage device 630 can be connected to the system bus 605. In some embodiments, a hardware module that performs a particular function can include a software component stored in a computer-readable medium in connection with the necessary hardware components, such as the processor 610, bus 605, output device 635, and so forth, to carry out the function.

FIG. 6B illustrates an example architecture for a chipset computing system 650 that can be used in accordance with an embodiment. The computing system 650 can include a processor 655, representative of any number of physically and/or logically distinct resources capable of executing software, firmware, and hardware configured to perform identified computations. The processor 655 can communicate with a chipset 660 that can control input to and output from the processor 655. In this example, the chipset 660 can output information to an output device 665, such as a display, and can read and write information to storage device 670, which can include magnetic media, solid state media, and other suitable storage media. The chipset 660 can also read data from and write data to RAM 675. A bridge 680 for interfacing with a variety of user interface components 685 can be provided for interfacing with the chipset 660. The user interface components 685 can include a keyboard, a microphone, touch detection and processing circuitry, a pointing device, such as a mouse, and so on. Inputs to the computing system 650 can come from any of a variety of sources, machine generated and/or human generated.

The chipset 660 can also interface with one or more communication interfaces 690 that can have different physical interfaces. The communication interfaces 690 can include interfaces for wired and wireless LANs, for broadband wireless networks, as well as personal area networks. Some applications of the methods for generating, displaying, and using the technology disclosed herein can include receiving ordered datasets over the physical interface or be generated by the machine itself by the processor 655 analyzing data stored in the storage device 670 or the RAM 675. Further, the computing system 650 can receive inputs from a user via the user interface components 685 and execute appropriate functions, such as browsing functions by interpreting these inputs using the processor 655.

It will be appreciated that computing systems 600 and 650 can have more than one processor 610 and 655, respectively, or be part of a group or cluster of computing devices networked together to provide greater processing capability.

For clarity of explanation, in some instances the various embodiments may be presented as including individual functional blocks including functional blocks comprising devices, device components, steps or routines in a method embodied in software, or combinations of hardware and software.

In some embodiments the computer-readable storage devices, mediums, and memories can include a cable or wireless signal containing a bit stream and the like. However, when mentioned, non-transitory computer-readable storage media expressly exclude media such as energy, carrier signals, electromagnetic waves, and signals per se.

Methods according to the above-described examples can be implemented using computer-executable instructions that are stored or otherwise available from computer readable media. Such instructions can include, for example, instructions and data which cause or otherwise configure a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. Portions of computer resources used can be accessible over a network. The computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, firmware, or source code. Examples of computer-readable media that may be used to store instructions, information used, and/or information created during methods according to described examples include magnetic or optical disks, flash memory, USB devices provided with non-volatile memory, networked storage devices, and so on.

Devices implementing methods according to these disclosures can include hardware, firmware and/or software, and can take any of a variety of form factors. Some examples of such form factors include general purpose computing devices such as servers, rack mount devices, desktop computers, laptop computers, and so on, or general purpose mobile computing devices, such as tablet computers, smart phones, personal digital assistants, wearable devices, and so on. Functionality described herein also can be embodied in peripherals or add-in cards. Such functionality can also be implemented on a circuit board among different chips or different processes executing in a single device, by way of further example.

The instructions, media for conveying such instructions, computing resources for executing them, and other structures for supporting such computing resources are means for providing the functions described in these disclosures.

A series of statements describing some examples is included below to provide clarity and understanding of the technology disclosed herein:

Statement 1: A method for mapping wireless access points to a building floor includes identifying a switch that is communicatively coupled to one or more wireless access points by a wired connection, generating a radio frequency cluster based on the one or more access points using receiver messages and transmission messages between respective neighboring access points, the radio frequency cluster including a group of access points within a broadcast range of each other, determining pairwise distances between each access point of the radio frequency cluster based on a path loss model, determining a portion of the radio frequency cluster that is on a shared floor with the identified switch based on the wired connection, determining wired distances of each access point from the switch based on a wire length calculated by a message travel time over the wired connection from the wireless access point to the switch, identifying respective locations of each access point relative to each other and the identified switch based on the wired distances, the pairwise distances, and respective trilateration information based on received signal strength indicators for each access point, the trilateration information generated by one or more deployed sensors, and overlaying the identified respective locations on a floor plan map.

Statement 2: The method of preceding Statement 1 may include the path loss model being a site specific path loss model for one of a building or geographic site corresponding to the floor plan map.

Statement 3: The method of any of the preceding Statements may include identifying the switch further including retrieving topological network information from a network management system, the topological network information including switch locations for a networked site.

Statement 4: The method of any of the preceding Statements may include determining an installation site for a new access point based on the identified respective locations overlaid on the floor plan map.

Statement 5: The method of any of the preceding Statements may include determining the portion of the radio frequency cluster further including mapping access points associated with the identified switch by using a link layer discovery protocol.

Statement 6: The method of any of the preceding Statements may include generating the receiver messages and the transmission messages including neighbor discovery frames.

Statement 7: The method of any of the preceding Statements may include displaying the overlaid identified respective locations on the floor plan map through a graphical user interface accessible by a network administrator.

Statement 8: A system for mapping wireless access points to a building floor includes one or more processors, and a memory comprising instructions to identify a switch that is communicatively coupled to one or more wireless access points by a wired connection, generate a radio frequency cluster based on the one or more access points using receiver messages and transmission messages between respective neighboring access points, the radio frequency cluster including a group of access points within a broadcast range of each other, determine pairwise distances between each access point of the radio frequency cluster based on a path loss model, determine a portion of the radio frequency cluster that is on a shared floor with the identified switch based on the wired connection, determine wired distances of each access point from the switch based on a wire length calculated by a message travel time over the wired connection from the wireless access point to the switch, identify respective locations of each access point relative to each other and the identified switch based on the wired distances, the pairwise distances, and respective trilateration information based on received signal strength indicators for each access point, the trilateration information generated by one or more deployed sensors, and overlay the identified respective locations on a floor plan map.

Statement 9: The system of preceding Statement 8 may include the path loss model being a site specific path loss model for one of a building or geographic site corresponding to the floor plan map.

Statement 10: The system of any of preceding Statements 8-9 may include identifying the switch further including retrieving topological network information from a network management system, the topological network information comprising switch locations for a networked site.

Statement 11: The system of any of preceding Statements 8-10 may include the memory further including instructions to determine an installation site for a new access point based on the identified respective locations overlaid on the floor plan map.

Statement 12: The system of any of preceding Statements 8-11 may include determining the portion of the radio frequency cluster further including mapping access points associated with the identified switch by using a link layer discovery protocol.

Statement 13: The system of any of preceding Statements 8-12 may include generating the receiver messages and the transmission messages including neighbor discovery frames.

Statement 14: The system of any of preceding Statements 8-13 may include the memory further including instructions to display the overlaid identified respective locations on the floor plan map through a graphical user interface accessible by a network administrator.

Statement 15: A non-transitory computer readable medium includes instructions which, when executed by one or more processors, cause the one or more processors to identify a switch that is communicatively coupled to one or more wireless access points by a wired connection, generate a radio frequency cluster based on the one or more access points using receiver messages and transmission messages between respective neighboring access points, the radio frequency cluster including a group of access points within a broadcast range of each other, determine pairwise distances between each access point of the radio frequency cluster based on a path loss model, determine a portion of the radio frequency cluster that is on a shared floor with the identified switch based on the wired connection, determine wired distances of each access point from the switch based on a wire length calculated by a message travel time over the wired connection from the wireless access point to the switch, identify respective locations of each access point relative to each other and the identified switch based on the wired distances, the pairwise distances, and respective trilateration information based on received signal strength indicators for each access point, the trilateration information generated by one or more deployed sensors, and overlay the identified respective locations on a floor plan map.

Statement 16: The non-transitory computer readable medium of preceding Statement 15 may include the path loss model being a site specific path loss model for one of a building or geographic site corresponding to the floor plan map.

Statement 17: The non-transitory computer readable medium of any of preceding Statements 15-16 may include identifying the switch further including retrieving topological network information from a network management system, the topological network information comprising switch locations for a networked site.

Statement 18: The non-transitory computer readable medium of any of preceding Statements 15-17 may include the instructions further causing the one or more processors to determine an installation site for a new access point based on the identified respective locations overlaid on the floor plan map.

Statement 19: The non-transitory computer readable medium of any of preceding Statements 15-18 may include determining the portion of the radio frequency cluster further including mapping access points associated with the identified switch by using a link layer discovery protocol.

Statement 20: The non-transitory computer readable medium of any of preceding Statements 15-19 may include generating the receiver messages and the transmission messages including neighbor discovery frames.

Although a variety of examples and other information was used to explain aspects within the scope of the appended claims, no limitation of the claims should be implied based on particular features or arrangements in such examples, as one of ordinary skill would be able to use these examples to derive a wide variety of implementations. Further and although some subject matter may have been described in language specific to examples of structural features and/or method steps, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to these described features or acts. For example, such functionality can be distributed differently or performed in components other than those identified herein. Rather, the described features and steps are disclosed as examples of components of systems and methods within the scope of the appended claims. 

What is claimed is:
 1. A method for mapping wireless access points to a building floor, the method comprising: identifying a switch that is communicatively coupled to one or more wireless access points by a wired connection; generating a radio frequency cluster based on the one or more access points using receiver messages and transmission messages between respective neighboring access points, the radio frequency cluster comprising a group of access points within a broadcast range of each other; determining pairwise distances between one or more pairs of access points of the radio frequency cluster based on a path loss model; determining a portion of the radio frequency cluster that is on a shared floor with the identified switch based on the wired connection; determining wired distances of each access point from the switch based on a wire length calculated by a message travel time over the wired connection from the wireless access point to the switch; identifying respective locations of each access point relative to each other and the identified switch based on the wired distances, the pairwise distances, and respective trilateration information based on received signal strength indicators for each access point, the trilateration information generated by one or more deployed sensors; and overlaying the identified respective locations on a floor plan map.
 2. The method of claim 1, wherein the path loss model is a site specific path loss model for one of a building or geographic site corresponding to the floor plan map.
 3. The method of claim 1, wherein identifying the switch further comprises retrieving topological network information from a network management system, the topological network information comprising switch locations for a networked site.
 4. The method of claim 1, further comprising determining an installation site for a new access point based on the identified respective locations overlaid on the floor plan map.
 5. The method of claim 1, wherein determining the portion of the radio frequency cluster further comprises mapping access points associated with the identified switch by using a link layer discovery protocol.
 6. The method of claim 1, wherein generating the receiver messages and the transmission messages comprises receiving and processing neighbor discovery frames.
 7. The method of claim 1, further comprising displaying the overlaid identified respective locations on the floor plan map through a graphical user interface accessible by a network administrator.
 8. A system for mapping wireless access points to a building floor, the system comprising: one or more processors; and a memory comprising instructions to: identify a switch that is communicatively coupled to one or more wireless access points by a wired connection; generate a radio frequency cluster based on the one or more access points using receiver messages and transmission messages between respective neighboring access points, the radio frequency cluster comprising a group of access points within a broadcast range of each other; determine pairwise distances between one or more pairs of access points of the radio frequency cluster based on a path loss model; determine a portion of the radio frequency cluster that is on a shared floor with the identified switch based on the wired connection; determine wired distances of each access point from the switch based on a wire length calculated by a message travel time over the wired connection from the wireless access point to the switch; identify respective locations of each access point relative to each other and the identified switch based on the wired distances, the pairwise distances, and respective trilateration information based on received signal strength indicators for each access point, the trilateration information generated by one or more deployed sensors; and overlay the identified respective locations on a floor plan map.
 9. The system of claim 8, wherein the path loss model is a site specific path loss model for one of a building or geographic site corresponding to the floor plan map.
 10. The system of claim 8, wherein identifying the switch further comprises retrieving topological network information from a network management system, the topological network information comprising switch locations for a networked site.
 11. The system of claim 8, wherein the memory further comprises instructions to determine an installation site for a new access point based on the identified respective locations overlaid on the floor plan map.
 12. The system of claim 8, wherein determining the portion of the radio frequency cluster further comprises mapping access points associated with the identified switch by using a link layer discovery protocol.
 13. The system of claim 8, wherein generating the receiver messages and the transmission messages comprises receiving and processing neighbor discovery frames.
 14. The system of claim 8, wherein the memory further comprises instructions to display the overlaid identified respective locations on the floor plan map through a graphical user interface accessible by a network administrator.
 15. A non-transitory computer readable medium comprising instructions which, when executed by one or more processors, cause the one or more processors to: identify a switch that is communicatively coupled to one or more wireless access points by a wired connection; generate a radio frequency cluster based on the one or more access points using receiver messages and transmission messages between respective neighboring access points, the radio frequency cluster comprising a group of access points within a broadcast range of each other; determine pairwise distances between one or more pairs of access points of the radio frequency cluster based on a path loss model; determine a portion of the radio frequency cluster that is on a shared floor with the identified switch based on the wired connection; determine wired distances of each access point from the switch based on a wire length calculated by a message travel time over the wired connection from the wireless access point to the switch; identify respective locations of each access point relative to each other and the identified switch based on the wired distances, the pairwise distances, and respective trilateration information based on received signal strength indicators for each access point, the trilateration information generated by one or more deployed sensors; and overlay the identified respective locations on a floor plan map.
 16. The non-transitory computer readable medium of claim 15, wherein the path loss model is a site specific path loss model for one of a building or geographic site corresponding to the floor plan map.
 17. The non-transitory computer readable medium of claim 15, wherein identifying the switch further comprises retrieving topological network information from a network management system, the topological network information comprising switch locations for a networked site.
 18. The non-transitory computer readable medium of claim 15, wherein the instructions further cause the one or more processors to determine an installation site for a new access point based on the identified respective locations overlaid on the floor plan map.
 19. The non-transitory computer readable medium of claim 15, wherein determining the portion of the radio frequency cluster further comprises mapping access points associated with the identified switch by using a link layer discovery protocol.
 20. The non-transitory computer readable medium of claim 15, wherein generating the receiver messages and the transmission messages comprises receiving and processing neighbor discovery frames. 